@rubencarneiro from which channel do you install your ROM? I guess channels need to be clarified (I, myself is a bit lost).

Hi,

Yes, and also, having some candles to light, before any USB plug... 😛
Again, I really want to thank you for your time. I finally can enjoy the UT experience, and maybe try to participate to it 🙂

Hi everybody:

I just want to share my experience with this issue today. Following the advice of @allaoua (who also helped me with this problem) I switched from devel_rc-proposed to stable 10 channel and finally I could make data work. The other problem (battery display) has also been rapaired by doing so although, as allaoua said, video isn't working but I don't really care because I can't even remember the last time a used it.

I hope this can help.
Best regards for everyone and keep going.

I remotely remember that there was a patch somewhere to make multirom use the ubports servers. MR itself has support for the format. Maybe you can dig that up.

Yes it seems to be a problem that is yet to be solved that others have.

There is a bug reported here: https://bugs.launchpad.net/ubports-android/+bug/1610707

I have this issue too. Is there a workaround?

N5. 16.04dev

@izd Hello,

maybe it is not well communicated but currently the devel_rc-proposed channel is the "stable" channel for N5. Did you try to flash that one, it should work pretty well.

We are about to shift devel to stable soon, as I already remarked internally that people will be irritated by the current stable channel´s broken state.

Please try to do that and tell us if it worked.

BR

We are the changelog writer 😉
Test it ! It's about 10mn installation and share what's works or not 🙂
Going back to Android is about the same duration, so, 1/2 hour is enough for all stuff !

Hey, I had the same problem (Nexus 5) and I think I know what is the cause for this problem. It is the same as @Bash-Horatio specified.

The device has two identifiers:

Google Android [0100] LGE Nexus 5[0232]

Now, whenever the device is on fastboot it is identified as Google Android [0100] but when it moves to Recovery mode it is identified as LGE Nexus 5[0232]. Seems like the script is loosing the connection to Google Android [0100] right when the device is going to recovery mode.

So, under VirtualBox you should go to Machine -> settings -> Ports -> USB. Check to "ON" the "Enable USB Controller" and "USB 1.1 (OHCI) Controller". On the right, there are small blue usb icons to add/remove usb filters. You should add two filters for each device identifier (i.e. Google Android [0100] and LGE Nexus 5[0232]).

How? Connect the device when it is NOT in fasboot and add a usb filter (should be LGE Nexus 5[0232]). After having this filter switch your device to fastboot and then add a new filter (should be Google Android [0100]).

Once you have two usb filters you can run the ubports.

For non-VirtualBox I would say that you should disconnect / connect the device when ever your phone switched to Recovery Mode so the script will recognize the device with its new identifier (LGE Nexus 5[0232]).

for me it worked fine after few hours of frustration...

Hope it will help.

A'aron

I have found help here : https://forum.xda-developers.com/google-nexus-5/general/port-ubuntu-touch-nexus-5-t2594874/page59
It's not difficult. It works with Android and Cyanogenmod.
If you do it, take some note and please write it on the wiki or on the forum asking for help to edit the wiki. That would help others.

I ended up installing ubuntu touch stable today to my nexus 5 (hammerhead) with
https://github.com/MariusQuabeck/magic-device-tool

and I got ubuntu 15.04 (r13) (20170127-093441 / 20160603- )

and if I start the browser in phone it crashes at once. That is pretty bad.

I have noticed that the there is OTA-15 out, but I guess that the magic-device-tool did not give me that version. Or did it, how I can check it ?

And does anyone know if magic-device-tool images will be updated in near future ?

So I'm using this as a notebook to keep track and also share progress.

Today I tried out the rootfs of 9-20-2016 has the display corruption.
So backing off to 7-28-2016 works fine as far as the display goes.

Now to do some testing on it I need to set the rootfs writable to be able to install more packages but I struggle to remember the utility to do it with.

To be continued....

In the end I managed to get it inot the bootloader manually, vol up + down then power on. I flashed the factory android 6 back on and then did a fresh install of rc-proposed.

there is still something wrong with it though as "adb reboot bootlader" does not work.

@tom
" I flashed ubuntu over the baseband of cm12.1. I thought that was what the advice was! "
Yes, I think that was the advice.

My cheap advice about mixing systems -> " dual booting is just not worth the trouble."

I just installed stable today and wireless working perfectly for me so far (D821e).

Not tried yet with my SIM in as waiting for a new screen for this damaged nexus 5 before swapping over from a nexus 4.

@rubencarneiro Contribute to the bug report if you can.

https://bugs.launchpad.net/ubports-android/+bug/1602916

I've tried every channel - each one I've tried had their own set of issues - battery life wasn't really a concern. In each channel I couldn't get location services to work - this was an issue with my Nexus 4 too but after switching to the bq channel it was fixed. I could never restart the phone without holding in the power button while it was trying to restart. I created my own Plex Webapp (using UT Tweak Tool from the Open App Store I can set it to not suspend so I can listen to my playlists with the screen off) works flawlessly on my Nexus 4 but on the Nexus 5 builds it will continually suspend and unsuspend causing the music to cut in and out. I had problems with the date and time not automatically updating after a restart which would set the time to generally January 4 1970 (I would have expected 12/31/69 but never got that date) - RC-Proposed would be slow but would set the date and time correctly. All the Devel channels had major screen tearing issues. Not being able to send (or upload them to OwnCloud) the few photos I took was also a slight annoyance I love UT can't wait for it to be more stable - I'd love to help anyway I could.